Device and method for handling messages

ABSTRACT

A device, method and system for handling received messages on a portable electronic device. The device includes a message handling section  12  to handle or route messages on the mobile device based upon whether the message is addressed to a port number assigned to an application on the mobile device. If the destination port number is not addressed to a port that is assigned to an application on the mobile device, and the message includes a link, then the message is opened automatically in a browser. Optionally, the link may be opened if the destination port number is within a range of port numbers or after requesting permission to open the message from the message recipient.

TECHNICAL FIELD OF THE INVENTION

The technology of the present disclosure relates generally to portablecommunication devices, and more particularly to a device and method bywhich a portable communication device handles received messages.

BACKGROUND

Portable electronic devices, such as mobile telephones, media players,personal digital assistants (PDAs), and others, are ever increasing inpopularity. To avoid having to carry multiple devices, portableelectronic devices are now being configured to provide a wide variety offunctions. For example, in addition to being used for making andreceiving telephone calls, a mobile telephone also may be used as acamera, an Internet browser for accessing news and information, anaudiovisual media player, a messaging device (text, audio, and/or visualmessages), a gaming device, a personal organizer, etc.

Additionally, portable communication devices may have the ability toaccess network-based applications over the Internet or another network.Exemplary network-based applications include email services, instantmessaging (IM) services, entertainment services, news and informationservices, and many others. Portable communication devices are capable ofsending and receiving messages intended for use with network-basedapplications. Typically, such messages include a link, for example, ahyperlink or Uniform Resource Locator (also referred to as a “URL”).

SUMMARY

Messages intended for network-based applications may be sent with simplemessage service (“SMS”). SMS messages typically are received in amessage inbox. The message generally must include human-readable text toallow the recipient to know the subject matter of the message and thetype of application to which it relates. This format, however, may notbe suitable for links to some network-based applications. Additionally,once an SMS message is directed to the inbox, a user may accidentallyforward the message to another device, which may be undesirable becausethe message may include confidential or private information intended forthe specific network-based application. After the message intended for anetwork-based application is directed to the inbox, the operation of theapplication automatically stops. The user must then manually select thelink in the message to restart the intended application.

SMS messages have a maximum length of 160 characters. The link or URLincluded in the message count against the 160 character limit. Thus, theinclusion of a link in a message limits the amount of space forproviding a personalized message and/or instructions to the messagerecipient. This length limit is particularly pronounced for messagesthat contain an especially long URL.

To improve the consumer experience with electronic devices, there is aneed in the art for an improved method and device for handling messages.

As described in more detail below, a device and method of handling amessage are disclosed. According to one aspect of the invention, amethod of handling a message with a mobile device includes receiving amessage on the mobile device, the message including a destination portnumber, determining whether an application on the mobile phone isassigned to the destination port number, and (i) in the event that anapplication is assigned to the destination port number, opening themessage with the application, and (ii) in the event that no applicationis assigned to the destination port number, determining if the messagecontains a link and automatically opening the link in a browser.

According to another aspect of the method, the message is an SMSmessage.

According to another aspect of the method, the link is a URL.

According to another aspect, the method further includes adding aparameter to the URL before automatically opening the link in thebrowser.

According to another aspect, the method further includes determining ifthe destination port number is within a range of port numbers, andautomatically opening the message in the browser in the event that thedestination port number is within a range of port numbers and themessage contains a link, or placing the message in the message inbox inthe event that the destination port number is not within the range ofport numbers.

According to another aspect of the method, the determining if thedestination port number is within a range of port number furtherincludes determining if the destination port number is a port numberbetween 16000-16999.

According to another aspect, the method further includes prompting theuser for permission before automatically opening the link in thebrowser.

According to another aspect of the method, the method further includesdisplaying information related to a sender of the message on a displayof the mobile device.

According to another aspect of the method, the link is a link to anetwork-based application.

According to another aspect of the invention, a mobile device includes amessage parser for parsing a data received in a message into a messagebody and a message header, wherein the message header includes adestination port number, and a message controller configured to (i)direct the message to an application, in the event that the applicationis assigned to the destination port number, and (ii) determine if themessage contains a link and to automatically open the link in a browserin the event that no application is assigned to the destination portnumber.

According to another aspect, the message is a SMS.

According to another aspect, the link is a URL.

According to another aspect of the mobile device, the message controlleris configured to add a parameter to the URL to indicate that the messagewas automatically opened in the browser.

According to another aspect of the mobile device, the message controlleris configured to automatically open the message in the browser if thedestination port number is within a range of port numbers and themessage includes a link, or to place the message in the message inbox ifthe destination port number is not within the range of port numbers.

According to another aspect of the mobile device, the range of portnumbers is port numbers 16000-16999.

According to another aspect of the mobile device, the message controlleris configured to prompt a user for permission before automaticallyopening the link.

According to another aspect, the mobile device further includes adisplay, wherein the message controller is configured to display atleast part of the message body on a display.

According to another aspect of the mobile device, the link is a link toa network-based application.

According to another aspect of the invention, a system includes acommunications network having an application server containing thenetwork-based application, and a user electronic device including: amessage parser configured to receive a message and to parse the messageinto a message header and a message body, wherein the message headerincludes a destination port number, and a message controller configuredto determine whether the destination port number is assigned to anapplication on the mobile device and to direct the message to theassigned application in the event that an application is assigned to thedestination port number and to determine if the message includes a linkto a network-based application and to open the link in a browser in theevent that no application is assigned to the destination port number.

According to another aspect of the system, the message controller isfurther configured to determine if the destination port number isindicative of a message from a third-party application, and toautomatically open the message in the browser if the message is withinthe range of port numbers.

These and further features will be apparent with reference to thefollowing description and attached drawings. In the description anddrawings, particular embodiments of the invention have been disclosed indetail as being indicative of some of the ways in which the principlesof the invention may be employed, but it is understood that theinvention is not limited correspondingly in scope. Rather, the inventionincludes all changes, modifications and equivalents coming within thescope of the claims appended hereto.

It should be emphasized that the term “comprises/comprising” when usedin this specification is taken to specify the presence of statedfeatures, integers, steps or components but does not preclude thepresence or addition of one or more other features, integers, steps,components or groups thereof.

Features that are described and/or illustrated with respect to oneembodiment may be used in the same way or in a similar way in one ormore other embodiments and/or in combination with or instead of thefeatures of the other embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic view of a mobile telephone as an exemplaryelectronic device for use in accordance with an embodiment of thepresent invention.

FIG. 2 is a schematic block diagram of operative portions of the mobiletelephone of FIG. 1.

FIG. 3 is a schematic block diagram of a message handling section of themobile telephone of FIG. 1.

FIG. 4 is a schematic diagram of an exemplary embodiment of acommunications system.

FIG. 5 is a schematic diagram of an exemplary embodiment of anapplication server in accordance with aspects of the present invention.

FIG. 6 is a flowchart depicting an exemplary method in accordance withaspects of the present invention.

FIG. 7 is a schematic diagram of a mobile telephone in accordance withaspects of the present invention.

DETAILED DESCRIPTION OF EMBODIMENTS

Embodiments are described with reference to the drawings, wherein likereference numerals are used to refer to like elements throughout. Itwill be understood that the figures are not necessarily to scale.

Referring initially to FIGS. 1 and 2, an exemplary portable electronicdevice 10 is shown. In accordance with aspects of the present invention,the electronic device 10 is configured with a message handling section12 to handle or route messages on the mobile device. The messagehandling section 12 receives each incoming message and determines if themessage is addressed to a specific port number (also referred to as a“destination port” or “destination port number”). The message handlingsection 12 then determines whether the destination port number isassigned to an application 14 on the device 10. If an application 14 isassigned to the destination port, the message is directed or routed tothat application. If an application is not registered to the destinationport number, then the message handling section 12 determines if themessage contains a link, for example, a URL or hyperlink, which may linkto a webpage where a network-based application can be accessed and used.

If the message contains a link, the link is automatically opened in thebrowser 16. The user may then download and install the network-basedapplication or use the application through the browser 16. The messagehandling section 12 assigns the destination port to the network-basedapplication so that future messages addressed to the destination portare automatically directed to or opened with the network-basedapplication. If the message does not include a link, the message isplaced in a message inbox.

Additional details and operation of the message handling section 12 willbe described in greater detail below. The message handling section 12may be embodied as executable code that is resident in and executed by acontrol circuit in the electronic device 10. In one embodiment, themessage handling section 12 may be a program stored on a computer ormachine readable medium. The message handling section 12 may be astand-alone software application or form a part of a softwareapplication that carries out additional tasks related to the electronicdevice 10. The message handling section 12 may be stored in memory 18and/or in firmware, as discussed below.

The electronic device of the illustrated embodiment is a mobiletelephone and will be referred to as the mobile telephone or mobiledevice 10. The mobile telephone 10 is shown as having a “brick” or“block” form factor housing, but it will be appreciated that otherhousing types may be utilized, such as a “flip-open” form factor (e.g.,a “clamshell” housing) or a slide-type form factor (e.g., a “slider”housing).

The mobile telephone 10 may include a display 20. The display 20displays information to a user such as operating state, time, telephonenumbers, contact information, various navigational menus, etc., througha graphical user interface (GUI) that enables the user to utilize thevarious features of the mobile telephone 10. The display 20 also may beused to visually display content received by the mobile telephone 10and/or retrieved from a memory 18 (FIG. 2) of the mobile telephone 10.The display 20 may be used to present images, video and other graphicsto the user, such as photographs, Internet content, text messages, userprompts, etc.

A keypad 21 provides for a variety of user input operations. Forexample, the keypad 21 typically includes alphanumeric keys for allowingentry of alphanumeric information such as telephone numbers, phonelists, contact information, notes, etc. In addition, the keypad 21typically includes special function keys such as a “call send” key forinitiating or answering a call, and a “call end” key for ending or“hanging up” a call. Special function keys also may include menunavigation and select keys to facilitate navigating through a menudisplayed on the display 20. For instance, a pointing device and/ornavigation keys may be present to accept directional inputs from a user.Special function keys may include audiovisual content playback keys tostart, stop and pause playback, skip or repeat tracks, and so forth.Other keys associated with the mobile telephone may include a volumekey, an audio mute key, an on/off power key, a web browser launch key, acamera key, etc. Keys or key-like functionality also may be embodied asa touch screen associated with the display 20. Also, the display 20 andkeypad 21 may be used in conjunction with one another to implement softkey functionality.

The mobile telephone 10 includes call circuitry that enables the mobiletelephone 10 to establish a call and/or exchange signals with acalled/calling device, typically another mobile telephone or landlinetelephone. The called/calling device need not be another telephone, butmay be some other device such as an Internet web server, contentproviding server, etc. Calls may take any suitable form. For example,the call could be a conventional call that is established over acellular circuit-switched network or a voice over Internet Protocol(VoIP) call that is established over a packet-switched capability of acellular network or over an alternative packet-switched network, such asWiFi (e.g., a network based on the IEEE 802.11 standard), WiMax (e.g., anetwork based on the IEEE 802.14 standard), etc. Another exampleincludes a video enabled call that is established over a cellular oralternative network.

The mobile telephone 10 may be configured to transmit, receive and/orprocess data, such as text messages (e.g., a text message is commonlyreferred to by some as “an SMS,” which stands for simple messageservice), instant messages, electronic mail messages, multimediamessages (e.g., a multimedia message is commonly referred to by some as“an MMS,” which stands for multimedia message service), image files,video files, audio files, ring tones, streaming audio, streaming video,data feeds (including podcasts) and so forth. Processing such data mayinclude storing the data in the memory 18, executing applications toallow user interaction with data, displaying video and/or image contentassociated with the data, outputting audio sounds associated with thedata and so forth.

The mobile phone 10 also may be configured to access network-basedapplications, also referred to as web-based applications or webapplications, which are accessed via a browser 16 through the Internetor another network connection. The network-based application may becoded in a browser supported language such as HTML, Java, JavaScript,and the like. Some network-based applications include webmail, web-basedinstant messaging, online auctions and online games.

FIG. 2 represents a functional block diagram of the mobile telephone 10.For the sake of brevity, generally conventional features of the mobiletelephone 10 will not be described in great detail herein. The mobiletelephone 10 includes a primary control circuit 22 that is configured tocarry out overall control of the functions and operations of the mobiletelephone 10. The control circuit 22 may include a processing device 24,such as a CPU, microcontroller or microprocessor. The processing device24 executes code stored in a memory (not shown) within the controlcircuit 22 and/or in a separate memory, such as the memory 18, in orderto carry out operation of the mobile telephone 10. The memory 18 may be,for example, one or more of a buffer, a flash memory, a hard drive, aremovable media, a volatile memory, a non-volatile memory, a randomaccess memory (RAM), or other suitable device.

The processing device 24 may execute code that implements the messagehandling section 12 and other application(s) 14 on the mobile device 10.It will be apparent to a person having ordinary skill in the art ofcomputer programming, and specifically in application programming formobile telephones or other electronic devices, how to program a mobiletelephone 10 to operate and carry out logical functions associated withthe message handling section 12. Accordingly, details as to specificprogramming code have been left out for the sake of brevity. Also, whilethe message handling section 12 is executed by the processing device 24in accordance with a preferred embodiment of the invention, suchfunctionality could also be carried out via dedicated hardware,firmware, software, or combinations thereof, without departing from thescope of the invention.

Continuing to refer to FIGS. 1 and 2, the mobile telephone 10 includesan antenna 26 coupled to a radio circuit 28. The radio circuit 28includes a radio frequency transmitter and receiver for transmitting andreceiving signals via the antenna 26 as is conventional. The radiocircuit 28 may be configured to operate in a mobile communicationssystem and may be used to send and receive data and/or audiovisualcontent. Receiver types for interaction with a mobile radio networkand/or broadcasting network include, but are not limited to, GSM, CDMA,WCDMA, GPRS, WiFi, WiMax, DVB-H, ISDB-T, etc., as well as advancedversions of these standards.

The mobile telephone 10 further includes a sound signal processingcircuit 30 for processing audio signals transmitted by and received fromthe radio circuit 28. Coupled to the sound processing circuit 30 are aspeaker 32 and a microphone 34 that enable a user to listen and speakvia the mobile telephone 10 as is conventional.

The radio circuit 28 and sound processing circuit 30 are each coupled tothe control circuit 22 so as to carry out overall operation. Audio datamay be passed from the control circuit 22 to the sound signal processingcircuit 30 for playback to the user. The audio data may include, forexample, audio data from an audio file stored by the memory 18 andretrieved by the control circuit 22, or received audio data such as inthe form of streaming audio data from a mobile radio service. The soundprocessing circuit 30 may include any appropriate buffers, decoders,amplifiers and so forth.

The display 20 may be coupled to the control circuit 22 by a videoprocessing circuit 36 that converts video data to a video signal used todrive the display 20. The video processing circuit 36 may include anyappropriate buffers, decoders, video data processors and so forth. Thevideo data may be generated by the control circuit 22, retrieved from avideo file that is stored in the memory 18, derived from an incomingvideo data stream that is received by the radio circuit 30 or obtainedby any other suitable method.

The mobile telephone 10 may further include one or more I/O interface(s)38. The I/O interface(s) 38 may be in the form of typical mobiletelephone I/O interfaces and may include one or more electricalconnectors. As is typical, the I/O interface(s) 38 may be used to couplethe mobile telephone 10 to a battery charger to charge a battery of apower supply unit (PSU) 40 within the mobile telephone 10. In addition,or in the alternative, the I/O interface(s) 38 may serve to connect themobile telephone 10 to a headset assembly (e.g., a personal handsfree(PHF) device) that has a wired interface with the mobile telephone 10.Further, the I/O interface(s) 38 may serve to connect the mobiletelephone 10 to a personal computer or other device via a data cable forthe exchange of data. The mobile telephone 10 may receive operatingpower via the I/O interface(s) 38 when connected to a vehicle poweradapter or an electricity outlet power adapter.

The mobile telephone 10 also may include a system clock 42 for clockingthe various components of the mobile telephone 10, such as the controlcircuit 22. The control circuit 22 may, in turn, carry out timingfunctions, such as timing the durations of calls, generating the contentof time and date stamps, and so forth.

The mobile telephone 10 may include a camera 44 for taking digitalpictures and/or movies. Image and/or video files corresponding to thepictures and/or movies may be stored in the memory 18. The mobiletelephone 10 also may include a position data receiver 46, such as aglobal positioning system (GPS) receiver, Galileo satellite systemreceiver or the like.

The mobile telephone 10 also may include a local wireless interface 48,such as an infrared transceiver and/or an RF interface (e.g., aBluetooth interface), for establishing communication with an accessory,another mobile radio terminal, a computer or another device. Forexample, the local wireless interface 48 may operatively couple themobile telephone 10 to a headset assembly (e.g., a personal hands-freedevice) in an embodiment where the headset assembly has a correspondingwireless interface.

The message handling section 12 is described in greater detail withadditional reference to FIG. 3. The message handling section 12 includesa message parser 60, a message controller 62, a message inbox 64, and asending section 66. The control circuit 22 directs messages, such as SMSmessages, received by the mobile device 10 to the message handlingsection 12, and specifically to the message parser 60.

The message parser 60 receives the message and parses the data in themessage into components, such as the message header and the messagepayload. The message header generally includes information that is usedto deliver the message, for example, the destination port, senderinformation, etc. The message payload generally includes the body of themessage, for example, alphanumeric characters or text, an image, a URL,etc. The message parser 60 directs the parsed message, including themessage header and the message payload to a message controller 62.Although shown in the illustrated embodiment as a message parser, itwill be appreciated that the content of the message may be determined inany conventional manner.

The message controller 62 controls the routing of the message on themobile device 10, for example, by directing the message to any number ofdestinations on the mobile device 10. Examples of destinations on themobile device 10 include any of the application 14 on the device 10, anetwork-based application, the browser 16, the message inbox 64, etc.

The destination of the message is determined by the message controller62 based upon the information contained in the message header. Certainprograms or application(s) 14 on the mobile device may be assigned orregistered to specific port numbers on the mobile device 10. After thedestination port for the received message is determined, the messagecontroller 62 determines if the port number is already assigned to anapplication 14 on the mobile device 10. If the destination port isalready assigned to an application 14, then the message is directed tothat application. If the destination port is not assigned to anapplication, then the message controller 62 evaluates the message todetermine if it contains a link.

The message controller 62 may determine if the message contains a linkby scanning or otherwise evaluating the data in the message for one or amore characters that are indicative of a link. In one embodiment, themessage controller 62 may include text recognition or other scanningsoftware to scan the message and to identify strings of alphanumericcharacters that are representative of a link. For example, the messagecontroller 62 may scan the message for a string of characters typicallyincluded in a URL, e.g., “http”, “.com”, “.net,” “://”, or anotherstring of characters that is indicative of a hyperlink.

If the message controller 62 determines that the message includes alink, then the link may be opened automatically in the browser 16, oralternatively, the message controller 62 may prompt the user forpermission to open the link in the browser 16. The message controller 62also may require the user to enter security credential, such as aconfirmation code, login, password, or ask a security question to theuser. Additionally, the message controller 62 may provide additionalinformation to the user to identify the sender of the message and thedestination of the link. For example, such information may include thesender's name, phone number or other contact information, the name ofthe application, a personalized message, etc.

If the message does not include a link or if the user does not allow themessage controller 62 to automatically open the message in the browser16, then the message controller 62 places the message into the messageinbox 64. The user of the mobile device 10 may then open and read themessage from the inbox 64, as is conventional. Furthermore, if themessage includes a link, the user may manually select the link from themessage inbox 64.

The message controller 62 also is configured to assign or to register anapplication to a port number. For example, if message contains a link toa network-based application, then the message controller 62 is operableto register or assign that destination port to the network-basedapplication. Thus, future messages addressed to that port will bedirected automatically to the network-based application.

If the message includes a destination port number, the messagecontroller 62 may be configured to determine whether the destinationport number is within a range of port numbers. The message controller 62may handle the message differently according to whether or not thedestination port number is within the range. Such a configuration may beadvantageous to avoid assigning the same port number to two differentapplications or to avoid reassigning a port number from an applicationon the mobile device to a new application that is distributed or spreadthrough a link in a message.

For example, third party applications may send messages to port numbers16000-16999. If the destination port of the received message is withinthe 16000-16999 range, then the message controller 62 knows that themessage is intended for a third party application and not an applicationthat may be installed already on the mobile device. The messagecontroller 62 may then determine whether the received message includes alink, as described above. If the destination port is not within the16000-16999 range, then the message controller may determine that themessage is not intended for a new application, and therefore, it may beunnecessary to scan the message for a link. If the port number is notwithin the range, the message controller 62 may place the receivedmessage in the message inbox 64. The 16000-16999 range of port number isexemplary in nature and it will be appreciated that any range of portnumbers may used.

As mentioned above, the links to web applications may be received in themessage inbox 64 and may be opened by manually selecting and opening thelink in the browser 16. The message controller 62 may distinguishbetween those links that are opened automatically and those links thatare manually selected and opened by the user by adding a parameter tothe link before opening the link in the browser 16. For example, if linkin the message is “http://somewhere.com/downloadApp”, a parameter may beadded to the message to make the link“http://somewhere.com/downloadApp?redirected=1”. Such a parameterindicates to the server that the message was manually selected andopened rather than automatically opened.

The message controller 62 and the sending section 66 are coupled tocontrol the sending of messages from the mobile device 10, as isconventional. The sending section 66 may include functionality relatedto the addressing of messages, including SMS messages, to other mobiledevices. For example, the sending section 66 may add header informationto messages before they are sent, including, for example, a destinationport number.

With additional reference to FIG. 5, the mobile telephone 10 may beconfigured to operate as part of a communications system 70. The system70 may include a communications network 72 having a communicationsserver 74 (or servers) for managing calls placed by and destined to themobile telephone 10, transmitting data to the mobile telephone 10 andcarrying out any other support functions.

The application server 74 is operable to provide information usable byelectronic devices (e.g., electronic devices 10, 80) that are coupled tothe communication network 70, and may, for example host or providenetwork-based applications, web-based applications and the like. Inaddition, the application server 74 may be combined with one or moreother servers to provide the functionality described herein.

With additional reference to FIG. 4, the application server 74 mayinclude an application database 82 for storing files associated with oneor more applications. For example, if the application is anentertainment application, the database may contain various media files,or if the application is an email messaging service and/or an instantmessaging service, the database may provide storage facilities forusers, or code to be executed associated with processing messages. Otherapplications may be associated with other database types in similarfashion. The application server also may have a data streamer 84 fortransmitting data files and information to users as required by theapplication. The application server also may include a controller 86 forcarrying out and coordinating the various functions of the server.

Referring back to FIG. 4, the communications network also includes ashort message service center 78 (also referred to as a “SMSC 78”) forprocessing SMS messages sent between users of mobile devices 10, 80 inthe communications network 72, as is known in the art. The SMSC 78routes and delivers text messages to the devices 10, 80 on thecommunications network 72.

The communications server 74, application server 76, and SMSC 78communicate with the mobile telephone 10 via a transmission medium. Thetransmission medium may be any appropriate device or assembly,including, for example, a communications tower (e.g., a cell tower),another mobile telephone, a wireless access point, a satellite, etc.Portions of the network may include wireless transmission pathways. Thenetwork 70 may support the communications activity of multiple mobiletelephones 10 and other types of end user devices. As will beappreciated, the server 72 may be configured as a typical computersystem used to carry out server functions and may include a processorconfigured to execute software containing logical instructions thatembody the functions of the server 72 and a memory to store suchsoftware.

The network 72 may support the communications activity of multiplemobile telephones 10, 80 and other types of end user devices. As will beappreciated, the servers 74, 76, and 78 may be configured as a typicalcomputer system used to carry out server functions and may include aprocessor configured to execute software containing logical instructionsthat embody the functions of the servers 74, 76, 78 and a memory tostore such software.

Referring to FIG. 6, logical operations to implement an exemplary method100 for handling a message in accordance with the message handlingsection 12 described above are shown. Additional optional features ofthe method handling section 12 are shown in dashed lines in thefunctional block diagram of FIG. 6.

The method of handling a message begins at block 102. At block 104, amessage is received by the mobile device 10. In this exemplaryembodiment, the message is a SMS message that includes a destinationport number.

At block 106, the message handling section 12 determines whether anapplication 14 is registered to the destination port. If an applicationis registered to the destination port, then the message is directed bythe message handling section 12 to the application that is registered tothe destination port. The message handling section 12 may cause theapplication to open on the mobile device 10, or may “wake” anapplication that may be running in the background of the device 10. Atblock 108, the message is received by the registered application.

If the destination port is not registered with an application, themethod proceeds to block 110. At block 110, the message handling section12 determines whether the message includes a link, such as a URL in themessage header or message payload, for example. If the message does notcontain a link, then the message is placed in the message inbox at block112 and the process ends at block 114. If the message contains a link,then the method proceeds to block 116 and the link is opened by thebrowser 16 and the method ends at block 118.

At optional block 120, the message handling section 12 determineswhether the destination port is within a range of port numbers. Forexample, it may be determined whether the destination port is within arange of port numbers assigned or reserved for third party applications,such as port numbers 16000-16999. An advantage to determining whetherthe destination port number is within the range of port numbers commonlyassigned to third party applications is to avoid registering anapplication to two different applications. Although the above-mentionedrange is a range that indicates a third party application, it will beappreciated that any range may be used, regardless of whether the rangeis indicative of third party applications, or of another type ofapplication. If the destination port number is within the specifiedrange, the method proceeds to block 110 to determine if the messagecontains a link. If the destination port number is not within the range,the message is placed in the message inbox at block 112 and the methodends at block 114.

At optional block 122, the message handling section 12 may prompt theuser and request permission to open the link in the message. Anexemplary request for permission to open the link is shown in FIG. 7.The request for permission may be displayed to the recipient on thedisplay 20 of the mobile device 10.

As illustrated in FIG. 7, the request may include a personalized messagefrom the sender. For example, the text may include an invitation to therecipient to open a web-based chat application and the link may includethe URL for an application server 74 where the web-based application ishosted. The information included in the request also may includeinformation related to the sender of the message, for example, thesender's name, phone number, email address, screen name, etc. Themessage also may include instructions to the recipient, for example, howto download or use the application or information related to features oradditional functions that may be available through the link in themessage. The information may be displayed as a webpage in the browser16, and may provide information in a user-friendly format.

If the recipient would like to open the link in the browser 16, then“yes” may be selected, and the link may be automatically opened in thebrowser 16 as shown in block 116. If the recipient does not wish to openthe link, then “no” may be selected and the message will placed in themessage inbox at block 112 and the method would end at block 114.

According to optional block 126, the message handling section 12 may beconfigured to add a parameter to the link before opening the link in thebrowser 16. For example, as described above, a parameter may indicate tothe application server 74 that the link was automatically opened or thatthe link was manually selected and opened by the user from the messageinbox 64.

Although the invention has been shown and described with respect to acertain preferred embodiment or embodiments, it is obvious thatequivalent alterations and modifications will occur to others skilled inthe art upon the reading and understanding of this specification and theannexed drawings. In particular regard to the various functionsperformed by the above described elements (components, assemblies,devices, compositions, etc.), the terms (including a reference to a“means”) used to describe such elements are intended to correspond,unless otherwise indicated, to any element which performs the specifiedfunction of the described element (i.e., that is functionallyequivalent), even though not structurally equivalent to the disclosedstructure which performs the function in the herein illustratedexemplary embodiment or embodiments of the invention. In addition, whilea particular feature of the invention may have been described above withrespect to only one or more of several illustrated embodiments, suchfeature may be combined with one or more other features of the otherembodiments, as may be desired and advantageous for any given orparticular application.

Although certain embodiments have been shown and described, it isunderstood that equivalents and modifications falling within the scopeof the appended claims will occur to others who are skilled in the artupon the reading and understanding of this specification.

1. A method of handling a message with a mobile device comprising:receiving a message on the mobile device, the message including adestination port number; determining whether an application on themobile device is assigned to the destination port number; and (i) in theevent that an application is assigned to the destination port number,opening the message with the application; and (ii) in the event that noapplication is assigned to the destination port number, determining ifthe message contains a link and if the message contains a linkautomatically opening the link in a browser or if the message does notcontain a link placing the message in a message inbox.
 2. The method ofclaim 1, wherein the message is an SMS message.
 3. The method of claim1, wherein the link is a URL.
 4. The method of claim 3, furthercomprising adding a parameter to the URL before automatically openingthe link in the browser.
 5. The method of claim 1, further comprisingdetermining if the destination port number is within a range of portnumbers; and automatically opening the message in the browser in theevent that the destination port number is within a range of port numbersand the message contains a link, or placing the message in the messageinbox in the event that the destination port number is not within therange of port numbers.
 6. The method of claim 5, wherein determining ifthe destination port number is within a range of port number furthercomprises determining if the destination port number is a port numberbetween 16000-16999.
 7. The method of claim 1, further comprisingprompting a user for permission before automatically opening the link inthe browser.
 8. The method of claim 7, further comprising displayinginformation related to a sender of the message on a display of themobile device.
 9. The method of claim 1, wherein the link is a link to anetwork-based application.
 10. A mobile device comprising: a messageparser for parsing a data received in a message into a message body anda message header, wherein the message header includes a destination portnumber; and a message controller configured to: (i) direct the messageto an application, in the event that the application is assigned to thedestination port number; and (ii) determine if the message contains alink and if the message contains a link automatically opening the linkin a browser in the event that no application is assigned to thedestination port number or if the message does not contain a linkplacing the message in a message inbox browser in the event that noapplication is assigned to the destination port number.
 11. The mobiledevice of claim 10, wherein the message is an SMS.
 12. The mobile deviceof claim 10, wherein the link is a URL.
 13. The mobile device of claim12, wherein the message controller is configured to add a parameter tothe URL to indicate that the message was automatically opened in thebrowser.
 14. The mobile device of claim 10, wherein the messagecontroller is configured to automatically open the message in thebrowser if the destination port number is within a range of port numbersand the message includes a link, or to place the message in the messageinbox if the destination port number is not within the range of portnumbers.
 15. The mobile device of claim 14, wherein the range of portnumbers is port numbers 16000-16999.
 16. The mobile device of claim 10,wherein the message controller is configured to prompt a user forpermission before automatically opening the link.
 17. The mobile deviceof claim 16, further comprising a display, wherein the messagecontroller is configured to display at least part of the message body ona display.
 18. The mobile device of claim 10, wherein the link is a linkto a network-based application.
 19. A system comprising: acommunications network having an application server containing anetwork-based application; and a user electronic device including: amessage parser configured to receive a message and to parse the messageinto a message header and a message body, wherein the message headerincludes a destination port number; and a message controller configuredto determine whether the destination port number is assigned to anapplication on the mobile device and to: direct the message to theassigned application in the event that an application is assigned to thedestination port number; and determine if the message includes a link toa network-based application and if the message contains a link openingthe link in a browser in the event that no application is assigned tothe destination port number or if the message does not contain a linkplacing the message in a message inbox in the event that no applicationis assigned to the destination port number.
 20. The system of claim 19,wherein the message controller is further configured to determine if thedestination port number is indicative of a message from a third-partyapplication, and to automatically open the message in the browser if themessage is within the range of port numbers.